Systems and methods for scheduling a memory command for execution based on a history of previously executed memory commands

ABSTRACT

A memory system is operated by maintaining a queue of memory commands to be executed, maintaining a list of previously executed memory commands, comparing local information associated with the commands to be executed with local information associated with the list of previously executed commands, and selecting one of the commands for execution from the queue of memory commands to be executed based on a result of the comparison.

CROSS REFERENCE TO RELATED APPLICATION

This application claims the benefit of and priority to Korean Patent Application No. 2008-47244, filed on May 21, 2008, in the Korean Intellectual Property Office, the disclosure of which is hereby incorporated herein by reference as if set forth in its entirety.

BACKGROUND OF THE INVENTION

The present invention relates generally to data processing systems and, more particularly, to the use of storage devices, such as memory systems in data processing systems.

Native Command Queuing (NCQ) is a technology that is designed to enhance the performance of Hard Disk Drives (HDDs) that use a Serial Advanced Technology Attachment (SATA) interface or other interface that supports command queuing. In particular, NCQ may allow a hard disk to internally optimize the order in which received read and write commands are executed, which may reduce unnecessary drive head movement and improve performance. Solid State Disk (SSD) devices, however, do not have the mechanical moving parts that are used in HDDs. As a result, NCQ techniques have not generally been applied to SSD devices.

SUMMARY

According to some embodiments of the present invention, a memory system is operated by maintaining a queue of memory commands to be executed, maintaining a list of previously executed memory commands, comparing local information associated with the commands to be executed with local information associated with the list of previously executed commands, and selecting one of the commands for execution from the queue of memory commands to be executed based on a result of the comparison.

In other embodiments, the local information comprises channel, way, Direct Memory Access (DMA) time, address translation time, and/or hardware timing information.

In still other embodiments, selecting one of the commands for execution comprises selecting the one of the commands for execution from the queue of memory commands to be executed that has a shortest expected blocking time.

In still other embodiments, selecting one of the commands for execution comprises beginning with the one of the previously executed memory commands that was most recently executed and proceeding until the command for execution is selected, performing the following: discarding candidate commands for execution that are associated with a same channel as the previously executed command when the remaining candidate commands are not all associated with the same channel, then discarding candidate commands that are associated with the same channel and way as the previously executed command when the remaining candidate commands are all associated with the same channel, but are not all associated with the same channel and way, then discarding candidate commands that have longest Direct Memory Access (DMA) times when the remaining candidate commands are all associated with the same channel and way.

In still other embodiments, selecting one of the commands for execution comprises selecting one of the commands for execution from the queue of memory commands to be executed that is associated with the same channel and way as a more recent previously executed command when each of the remaining candidate commands are associated with the same channel and way as at least one of the previously executed commands.

In still other embodiments, DMA times are calculated based on memory sector size and/or sector count.

In still other embodiments, the channel and way are derived from Logical Block Address (LBA) information.

In still other embodiments, the method further comprises removing one of the previously executed commands from the list of previously executed memory commands when all operations associated with the one of the previously executed commands have completed.

In still other embodiments, command execution comprises address translation.

In still other embodiments, the list of previously executed memory commands is a circular list.

In still other embodiments, at least one of the above-described methods is performed by a Flash Translation Layer (FTL).

In still other embodiments, the memory comprises a flash memory.

In still other embodiments, the flash memory comprises a NAND, NOR, and/or a One_NAND type flash memory.

In further embodiments of the present invention, a memory system comprising a host, a memory controller, and a memory is operated by sending memory commands from the host to the memory controller, determining an execution order for the memory commands based on a history of previously executed memory commands, sending write data from the host to the memory controller while determining the execution order, writing the write data from the memory controller to the memory, reading read data from the memory into the memory controller, and sending the read data from the memory controller to the host.

In still further embodiments, determining the execution order comprises maintaining a queue of the memory commands to be executed, maintaining a list of the previously executed memory commands, comparing local information associated with the memory commands to be executed with local information associated with the list of previously executed memory commands, and selecting one of the memory commands for execution from the queue of memory commands to be executed based on a result of the comparison.

In still further embodiments, the local information comprises channel, way, Direct Memory Access (DMA) time, address translation time, and/or hardware timing information.

In still further embodiments, the memory comprises a flash memory.

In still further embodiments, the flash memory comprises a NAND, NOR, and/or a One_NAND type flash memory.

In other embodiments of the present invention, a memory system, comprises a memory and a memory controller that is configured to maintain a queue of commands for the memory to be executed, maintain a list of previously executed memory commands; compare local information associated with the commands to be executed with local information associated with the list of previously executed commands; and select one of the commands for execution from the queue of memory commands to be executed based on a result of the comparison.

In still other embodiments, the local information comprises channel, way, Direct Memory Access (DMA) time, address translation time, and/or hardware timing information.

In still other embodiments, the memory comprises a flash memory.

In still other embodiments, the flash memory comprises a NAND, NOR, and/or a One_NAND type flash memory.

In still other embodiments, the memory system is embodied in a memory card device, Solid State Drive (SSD) device, ATA bus device, Serial ATA (SATA) bus device, Small Computer System Interface (SCSI) device, Serial Attached SCSI (SAS) device, Multi-Media Card (MMC) device, Secure Digital (SD) device, memory stick device, Hard Disk Drive (HDD) device, Hybrid Hard Drive (HHD) device, and/or a Universal Serial Bus (USB) flash drive device.

In still other embodiments, the memory system is embodied in a graphics card, a computer, a mobile terminal, a Personal Digital Assistant (PDA), a camera, a game console, an MP3 player, a television, a DVD player, a router, and/or a GPS system.

Other systems and methods according to embodiments of the invention will be or become apparent to one with skill in the art upon review of the following drawings and detailed description. It is intended that all such additional systems and methods be included within this description, be within the scope of the present invention, and be protected by the accompanying claims.

BRIEF DESCRIPTION OF THE DRAWINGS

Other features of the present invention will be more readily understood from the following detailed description of specific embodiments thereof when read in conjunction with the accompanying drawings, in which:

FIG. 1 is a block diagram of a memory system according to some embodiments of the present invention;

FIG. 2 is a block diagram that illustrates a memory of the memory system of FIG. 1 in accordance with some embodiments of the present invention;

FIGS. 3A and 3B are block diagrams that illustrate read operations in the memory system of FIG. 1 according to some embodiments of the present invention;

FIGS. 4A, 4B, and 4C are block diagrams that illustrate write operations in the memory system of FIG. 1 according to some embodiments of the present invention;

FIG. 5 is a block diagram of a memory system according to further embodiments of the present invention;

FIG. 6 is a block diagram that illustrates a memory command history according to some embodiments of the present invention;

FIG. 7 is a block diagram that illustrates methods for selecting a memory command for execution according to some embodiments of the present invention;

FIG. 8 is a message flow diagram that illustrates operations of a memory system in which a memory command is selected for execution based on a history of previously executed memory commands;

FIGS. 9 and 10 illustrate experimental results in which write request commands and read request commands are performed on a memory system in accordance with some embodiments of the present invention; and

FIG. 11 is a block diagram of an electronic system that incorporates a memory system according to some embodiments of the present invention.

DETAILED DESCRIPTION OF EMBODIMENTS

While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that there is no intent to limit the invention to the particular forms disclosed, but on the contrary, the invention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the invention as defined by the claims. Like reference numbers signify like elements throughout the description of the figures.

As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless expressly stated otherwise. It should be further understood that the terms “comprises” and/or “comprising” when used in this specification is taken to specify the presence of stated features, integers, steps, operations, elements, and/or components, but does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being “connected” or “coupled” to another element, it can be directly connected or coupled to the other element or intervening elements may be present. Furthermore, “connected” or “coupled” as used herein may include wirelessly connected or coupled. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

For purposes of illustration, various embodiments of the present invention are described herein with reference to a memory system comprising a flash memory data storage device. It will be understood that the data storage device is not limited to implementation as a flash memory device, but can be implemented generally as an erase before write memory device. Also, it will be understood that the data storage device is not limited to implementation as a non-volatile memory device, and can be implemented as a volatile memory device, such as a dynamic random access memory (DRAM), and so on. The data storage device may be a memory card device, Solid State Drive (SSD) device, ATA bus device, Serial ATA (SATA) bus device, Small Computer System Interface (SCSI) device, Serial Attached SCSI (SAS) device, Multi-Media Card (MMC) device, Secure Digital (SD) device, memory stick device, Hard Disk Drive (HDD) device, Hybrid Hard Drive (HHD) device, and/or a Universal Serial Bus (USB) flash drive device.

According to some embodiments of the present invention, a memory system, such as, for example, a Solid State Disk (SSD) device, that includes a memory controller and a memory can be operated by maintaining a queue of memory commands to be executed along with a list of previously executed memory commands. A comparison can be made between the commands to be executed and those commands that have been previously executed to select the next command for execution in such that the expected blocking may be reduced, which may enhance the performance of the memory system.

Referring now to FIG. 1, an electronic apparatus comprises an SSD memory system 500 and a host 900 that communicate using, for example, the Serial Advanced Technology Attachment (SATA) protocol or other protocol that supports command queuing. Native Command Queuing (NCQ) and Tagged Command Queuing (TCQ) may be used in some embodiments of the present invention for command queuing. The SSD 500 comprises an SSD controller 100 and a flash memory 300. The flash memory 300 will be described as an example where embodiments of the present invention may be applied. However, the flash memory 300 to be described is not limited to a specific form, or program or read characteristic of the flash memory of the present invention. The flash memory 300 comprises multiple flash chips 310, 320, . . . 330 that are associated with communication channels CH_0, CH_1, and CH_(N-1), respectively. In addition, there may be multiple flash chips associated with each communication channel. Flash chips associated with the same channel may be identified by Way number. A management grouping for channels in a flash memory system is sometimes called a “unit,” and a management grouping for Ways in a flash memory system is sometimes called a “bank.” The controller 100 may be configured to store the command history 50 for the flash memory 300 and to schedule the execution of commands received from the host 900. In some embodiments of the present invention, the controller 100 selects a memory command for execution that has the shortest expected blocking time based on the command history 50 of previously executed memory commands. In some embodiments, blocking time refers to the waiting time caused by a communication channel being busy or a flash memory chip being busy. The communication interface between the host 900 and the memory system 500 may support Native Command Queuing (NCQ) or other command queuing method to allow the host 900 to transmit multiple memory commands without interruption. Some embodiments of the present invention may be applied to systems in which memory command queuing is supported and multiple communication channels are configured between the controller 100 memory and the flash 300 memory.

FIG. 2 is a block diagram that illustrates the flash memory 300 of FIG. 1 in more detail according to some embodiments of the present invention. As shown in FIG. 2, the flash memory 300 comprises multiple flash chips 310, 320, . . . 330 that are associated with communication channels CH_0, CH_1, and CH_(N-1), respectively. Each communication channel may operate independently of the other communication channels. Flash chips that are share the same communication channel are differentiated by Way number. According to some embodiments of the present invention, each chip in the flash memory 300 may be identified by Way and communication channel, which can be calculated based on the Logical Block Address (LBA). In some embodiments, the flash memory 300 is a NAND, NOR, and/or a One_NAND type flash memory.

FIGS. 3A and 3B are block diagrams that illustrate the timing requirements when executing multiple read commands on the SSD 500 of FIG. 1. As used in FIGS. 3A and 3B, f/w denotes the time associated with firmware operations, tR denotes the read time from the memory cell to a register inside the flash memory 300, and tRE denotes the read time from the register inside the flash memory 300 to the RAM inside the controller 100. As shown in FIG. 3A, when multiple read commands are directed to the flash memory 300 on different communication channels, the read commands can be executed in parallel. In FIG. 3A, the time f/w associated with firmware operations of the read commands on different communication channels may or may not the same to each other. For example, the directed read commands may be executed at the same time on the different communication channels. In addition, the directed read commands may be executed at different timing to each other for waiting for completion of the previously executed command on each of communication channels. As shown in FIG. 3B, however, when multiple read commands are directed to the flash memory 300 on the same communication channel, the second read command is blocked until the first read command completes the read from the flash 300 register to the RAM inside the controller 100.

FIGS. 4A, 4B, and 4C are block diagrams that illustrate the timing requirements when executing multiple write commands on the SSD 500 of FIG. 1. As used in FIGS. 4A, 4B, and 4C, tWE denotes the write time from the RAM inside the controller 100 to the page buffer inside the flash memory 300 and tPROG denotes the write time from the page buffer to the cell array inside the flash memory 300. As shown in FIG. 4A, when multiple read and/or write commands are directed to the flash memory 300 on different communication channels, the read and/or write commands can be executed in parallel. In FIG. 4A, the time f/w associated with firmware operations of the read and/or write commands on different communication channels may or may not the same to each other. For example, the directed read and/or write commands may be executed at the same time on the different communication channels. In addition, the directed read and/or write commands may be executed at different times relative to each other for waiting for completion of the previously executed read and/or write command on each of communication channels. As shown in FIG. 4B, however, when multiple read and/or write commands are directed to the flash memory 300 on the same communication channel, but different Ways, the read operation is blocked until write operation completes the write from the RAM inside the controller 100 to the page buffer inside the flash memory 300. As shown in FIG. 4C, when multiple read and/or write commands are directed to the flash memory 300 on the same communication channel and same ways, the read operation is blocked until the write operation completes the write from the RAM inside the controller 100 to the page buffer inside the flash memory 300 as well as the write from the page buffer to the cell array inside the flash memory 300. In FIGS. 4A, 4B, and 4C, the time tR is not needed if writing a whole page; however, when writing a partial page, a modified copy back operation is performed where data is read first into the page buffer inside the flash memory 300, additional data is written to the page buffer, and then the page buffer is written to the cell array.

FIG. 5 is a detailed block diagram of the SSD 500 according to some embodiments of the present invention. The controller 100 comprises a CPU 110, a working memory 120 that includes a command history 50, a host interface 140, which includes a register 150 for communicating commands/data between the controller 100 and a host, a buffer memory control unit 160, and a flash interface 180, which includes a register 190 for communicating commands/data between the controller 100 and the flash memory 300. The various controller 100 components communicate via a CPU bus 130. The host interface 140 may be configured to communicate using various interface protocols, such as USB, MMC, peripheral component interconnection bus-express (PCI-E), advanced technology attachment (ATA), serial-ATA (SATA), parallel-ATA, small computer system interface (SCSI), SAS (Serial Attached SCSI), enhanced small device interface (ESDI), and integrated driver electronics (IDE). The host interface 140 may support a protocol that supports command queuing, such as the SATA protocol, the SCSI protocol, and the SAS protocol. The buffer memory 170 may be configured to store the data transmitted between the flash memory 300 and the host 900 and also to store the command history 50′, which may also be stored in the working memory 120 as command history 50 in some embodiments of the present invention. Thus, the command history may be stored in one or both of the working memory 120 and the buffer memory 170 in accordance with various embodiments of the present invention. The buffer memory 170 may be located on an internal area of the SSD controller 100, and may be located on an external area of the SSD controller 100. The host interface 140 may be configured to transform the address to a LBA. The Flash Translation Layer (FTL) in the working memory 120 may be configured to translate the LBA to a Physical Block Address (PBA). The FTL may be configured to use the command history 50 and/or 50′ to schedule a memory command for execution that has a reduced or in some cases shortest expected blocking time. The memory scheduled command along with the PBA are transmitted to the flash memory 300 via the register 190 in the flash interface 180.

FIG. 6 is a block diagram that illustrates a memory command history according to some embodiments of the present invention. As shown in FIG. 6, each command 51-56 in the command history queue or list may comprise such local information as channel, Way, Direct Memory Access (DMA) time, and whether the command is a read or write command according to some embodiments of the present invention. In other embodiments, the local information may also comprise address translation time and/or hardware timing information. DMA times may be based on memory sector size and/or sector count. A previously executed command may be removed from the list when all operations associated with the command have completed. In some embodiments, the command history queue may be a circular queue. A command may be considered as having been executed after address translation has been completed even though the full operation, such as the write operation into the flash cell array, has not yet completed, according to some embodiments of the present invention.

Exemplary operations for selecting a memory command for execution according to some embodiments of the present invention will now be described by way of example with reference to block diagrams of FIGS. 6 and 7. FIG. 6 illustrates a memory command history list and FIG. 7 illustrates a queue of candidate memory commands 150 for execution according to some embodiments of the present invention. According to some embodiments of the present invention, the FTL module may be configured to compare local information associated with the list of candidate memory commands to be executed shown in FIG. 7 with the local information associated with the list of previously executed commands shown in FIG. 6 so as to select a command for execution that has a reduced or shortest expected blocking time.

Referring to FIGS. 6 and 7, operations begin by the FTL examining the command 55 and determining that it was executed on channel 2. The FTL then discards candidate command 143 from the candidate queue of FIG. 7 because it is also designated for channel 2. Next, the FTL examines command 54 in FIG. 6 to determine that it was executed on channel 1. The FTL then discards candidate command 142 from the candidate queue of FIG. 7 because it is also designated for channel 1. Next, the FTL examines command 53 in FIG. 6 to determine that it was executed on channel 3. The FTL then discards candidate command 144 from the candidate queue of FIG. 7 because it is also designated for channel 3. Next, the FTL examines command 52 in FIG. 6 to determine that it was executed on channel 0. The FTL then determines that the remaining candidate commands 141 and 145 are both designated for channel 0. The FTL examines command 51 of FIG. 6 and determines that it also was executed on channel 0; however, command 51 was designated for Way 0 while command 52 was designated for Way 1. The candidate commands 141 and 145 of FIG. 7; however are designated for Way 0 and Way 1, respectively. The FTL then examines the DMA times associated with commands 51 and 52 to determine that command 51 has a DMA time of 15 μs while command 52 has a DMA time of 30 μs. Because the previously executed command 51 on channel 0, Way 0 has a shorter DMA time than the previously executed command 52 on channel 0, Way 1, the FTL discards candidate command 145 designated for channel 0, Way 1 and selects candidate command 141 on channel 0, way 0 for execution. After selecting the candidate command 141 for execution, the local information 56 corresponding to the candidate command 141 is stored in the command history queue or list in FIG. 6. In some embodiments, if the best candidate command for execution ends up being a write commands associated with the same channel and way as a previous write command, then the preferred candidate command may be a command that conflicts with a more recent previously executed command in history, particularly if the more recently executed command was a read command as read commands take less time to complete than a write command. In another axemplary operations for selecting a memory command for execution according to some embodiments of the present invention, the read and/or write commands may be executed in channels being completed the previous read and/or write command by monitoring the channel conditions by the FTL. In addition, the read and/or write commands may be executed first on channels having free way(s) based on the monitoring results of the channel conditions by the FTL.

FIG. 8 is a message flow diagram that illustrates operations of a memory system in which a memory command is selected for execution based on a history of previously executed memory commands in accordance with some embodiments of the present invention. The host 900 sends a read and a write NCQ command request to the controller 100 (S1100) through a host interface supporting a protocol that supports command queuing, such as the SATA protocol, the SCSI protocol, and the SAS protocol. The controller 100 responds with acknowledgements (S1200). The controller 100 then sends a request to the host for a DMA setup for the write operation (S1300). The timing for the DMA setup varies based on command. In the case of a write command, the controller 100 requests DMA setup after the NCQ command is generated to get the write data. The DMA setup can be requested during NCQ command scheduling at the controller 100. When the controller 100 sends the DMA setup request to the host 900, the host sends the write data to the controller 100 (S1400). The controller 100 may store the write data in the buffer memory 170. While the controller 100 stores the write data in the buffer memory, the FTL schedules the received NCQ commands for execution as described above with respect to FIGS. 6 and 7 (S2200). In a dual processor system, for example, the controller 100 may schedule another command before the FTL completes the mapping operation between LBA and PBA. The scheduled command is then executed on the memory 300 (S2300). In the case of a write command, the write data is provided from the buffer memory in the controller 100 to the memory 300 (S2400). In the case of a read command, the data read from the memory 300 is stored in the buffer memory in the controller 100 (S2500). The controller 100 sends a request to the host 900 for DMA setup for the read command (S1600). The controller 100 then provides the read data stored in the buffer memory to the host 900 (S1700).

FIGS. 9 and 10 illustrate experimental results in which write request commands and read request commands are performed on a memory system in accordance with some embodiments of the present invention. As shown in FIG. 9, the time to perform an 8 KB random write may be reduced from 879 μs to 630 μs using memory command reordering according to some embodiments of the present invention. As shown in FIG. 10, the time to perform an 8 KB random read may be reduced from 557 μs to 321 μs using memory command reordering according to some embodiments of the present invention.

FIG. 11 is a block diagram illustrates an electronic system, such as a computer system, that incorporates a memory system in accordance with some embodiments of the present invention. As shown in FIG. 11, the electronic system may include a microprocessor host 900, user interface 800, battery 700, SSD 500, which comprises an SSD memory controller 100 having a list of previously executed memory commands 50 stored therein and memory 300 (e.g., flash memory), and a modem 600 that are coupled to each other via an address/data bus. The controller 100 and memory 300 may be embodied as described above with respect to FIGS. 1-10. Thus, memory systems including the controller 100 and memory 300, according to some embodiments of the present invention, may be embodied in electronic systems, such as, but not limited to, a graphics card, a computer, a mobile terminal, a Personal Digital Assistant (PDA), a camera, a game console, an MP3 player, a television, a DVD player, a router, and/or a GPS system.

The SSD memory controller 100 and/or the memory 300, according to some embodiments of the present invention, may be placed on the computer system via a variety of package types including Package-on-Package (PoP), Ball Grid Arrays (BGAs), Chip Scale Packages (CSPs), Plastic Leaded Chip Carrier (PLCC), Plastic Dual In-line Package (PDIP), Die in Waffle Pack, Die in Wafer Form, Chip-On-Board (COB), CERamic Dual In-line Package (CERDIP), Plastic Metric Quad Flat Pack (MQFP), Thin Quad Flat Pack (TQFP), Small Outline (SOIC), Shrink Small Outline Package (SSOP), Thin Small Outline (TSOP), Thin Quad Flat Pack (TQFP), System In Package (SIP), Multi-Chip Package (MCP), Wafer-level Fabricated Package (WFP), Wafer-level Processed Stack Package (WSP), and/or Wafer-level Processed Package (WSP), among others. In some embodiments, the memory cells of the flash memory device 100 may be structured in various forms having charge storage layers. A charge storage architecture of the flash memory device may be implemented by including charge-trapping layers, stacked cell arrays where plural cell arrays are stacked, flash structures without source and drain regions, and/or pin-type flash structures, among others.

Many variations and modifications can be made to the embodiments without substantially departing from the principles of the present invention. All such variations and modifications are intended to be included herein within the scope of the present invention, as set forth in the following claims. 

1. A method of operating a memory system, comprising: maintaining a queue of memory commands to be executed; maintaining a list of previously executed memory commands; comparing local information associated with the commands to be executed with local information associated with the list of previously executed commands; and selecting one of the commands for execution from the queue of memory commands to be executed based on a result of the comparison.
 2. The method of claim 1, wherein the local information comprises channel, way, Direct Memory Access (DMA) time, address translation time, or hardware timing information.
 3. The method of claim 1, wherein selecting one of the commands for execution comprises selecting the one of the commands for execution from the queue of memory commands to be executed that has a shortest expected blocking time.
 4. The method of claim 1, wherein selecting one of the commands for execution comprises: beginning with the one of the previously executed memory commands that was most recently executed and proceeding until the command for execution is selected, performing the following: discarding candidate commands for execution that are associated with a same channel as the previously executed command when the remaining candidate commands are not all associated with the same channel; then discarding candidate commands that are associated with the same channel and way as the previously executed command when the remaining candidate commands are all associated with the same channel, but are not all associated with the same channel and way; then discarding candidate commands that have longest Direct Memory Access (DMA) times when the remaining candidate commands are all associated with the same channel and way.
 5. The method of claim 4, wherein selecting one of the commands for execution comprises selecting one of the commands for execution from the queue of memory commands to be executed that is associated with the same channel and way as a more recent previously executed command when each of the remaining candidate commands are associated with the same channel and way as at least one of the previously executed commands.
 6. The method of claim 4, wherein DMA times are calculated based on memory sector size or sector count.
 7. The method of claim 4, wherein the channel and way are derived from Logical Block Address (LBA) information.
 8. The method of claim 1, further comprising: removing one of the previously executed commands from the list of previously executed memory commands when all operations associated with the one of the previously executed commands have completed.
 9. The method of claim 1, wherein command execution comprises address translation.
 10. The method of claim 1, wherein the list of previously executed memory commands is a circular list.
 11. The method of claim 1, wherein the method is performed by a Flash Translation Layer (FTL).
 12. The method of claim 1, wherein the memory comprises a flash memory.
 13. The method of claim 12, wherein the flash memory comprises a NAND, NOR, or a One_NAND type flash memory.
 14. A method of operating a memory system comprising a host, a memory controller, and a memory, the method comprising: sending memory commands from the host to the memory controller; determining an execution order for the memory commands based on a history of previously executed memory commands; sending write data from the host to the memory controller while determining the execution order; writing the write data from the memory controller to the memory; reading read data from the memory into the memory controller; and sending the read data from the memory controller to the host.
 15. The method of claim 14, wherein determining the execution order comprises: maintaining a queue of the memory commands to be executed; maintaining a list of the previously executed memory commands; comparing local information associated with the memory commands to be executed with local information associated with the list of previously executed memory commands; and selecting one of the memory commands for execution from the queue of memory commands to be executed based on a result of the comparison.
 16. The method of claim 15, wherein the local information comprises channel, way, Direct Memory Access (DMA) time, address translation time, or hardware timing information.
 17. The method of claim 14, wherein the memory comprises a flash memory.
 18. The method of claim 17, wherein the flash memory comprises a NAND, NOR, or a One_NAND type flash memory.
 19. A memory system, comprising: a memory; and a memory controller that is configured to maintain a queue of commands for the memory to be executed, maintain a list of previously executed memory commands; compare local information associated with the commands to be executed with local information associated with the list of previously executed commands; and select one of the commands for execution from the queue of memory commands to be executed based on a result of the comparison.
 20. The system of claim 19, wherein the local information comprises channel, way, Direct Memory Access (DMA) time, address translation time, or hardware timing information.
 21. The system of claim 19, wherein the memory comprises a flash memory.
 22. The system of claim 21, wherein the flash memory comprises a NAND, NOR, or a One_NAND type flash memory.
 23. The memory system of claim 19, wherein the memory system is embodied in a memory card device, Solid State Drive (SSD) device, ATA bus device, Serial ATA (SATA) bus device, Small Computer System Interface (SCSI)device, Serial Attached SCSI (SAS) device, Multi-Media Card (MMC) device, Secure Digital (SD) device, memory stick device, Hard Disk Drive (HDD) device, Hybrid Hard Drive (HHD) device, or a Universal Serial Bus (USB) flash drive device.
 24. The memory system of claim 19, wherein the memory system is embodied in a graphics card, a computer, a mobile terminal, a Personal Digital Assistant (PDA), a camera, a game console, an MP3 player, a television, a DVD player, a router, or a GPS system. 